Minor update -> testing with redisvl#1
Merged
Conversation
abrookins
approved these changes
Jan 27, 2026
| strategy: | ||
| matrix: | ||
| python-version: | ||
| - "3.9" |
Contributor
There was a problem hiding this comment.
I might keep 3.10 and remove 3.9 here. Due to end-of-life timelines and such.
Contributor
Author
There was a problem hiding this comment.
Heard. I relaxed because it was causing a dep graph issue since redisvl allows for lower version now
| strategy: | ||
| fail-fast: false | ||
| matrix: | ||
| python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"] |
Contributor
There was a problem hiding this comment.
Same here, would remove 3.9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm experimenting with adding this package as an optional dep to redisvl.
Meaning
pip install redisvl[sql]would allow for theSQLQueryclass which would utilize this package under the hood. After thinking about it for a bit, I think this would be the correct way to package since redisvl should not own code for SQL->Redis type queries. However, since it's within redisvl purview to make it easier to interact with complex query interaction I believe the class there will make a lot of sense (and be popular).To this goal, I've added linting and other stuff to this repo so it gets a bit more polish if we do move towards a more generalized release.